home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
tribbs
/
secck20.zip
/
HISTORY.DOC
< prev
next >
Wrap
Text File
|
1996-05-28
|
6KB
|
109 lines
05/28/96 - Security Check! v2.0 Released to Public
The config file has changed.. Please refer to the example
secure.cfg file and compare it to your existing config files for
changes that were made. Also this is documented in the Secure.doc
file.
NEW for All Users:
Security Check now uses a new Key file and previous registered
users will have to request a new key file..
Security Check now uses different formats for the questions
when it grabs a caller for checking..
Date Of Birth's Format used to be: MMDDYY
Now it uses a Format like: MM/DD/YY
Phone Number Format used to be: ##########
Now it uses a Format like: ###-###-####
Hopefully this is more accustom to what callers are used to
and will help eliminate confusion.. :)
NEW for Registered Users:
Security Check now writes information to the TriBBS Callers.log
file. It will write infomation stating a caller was selected,
any incorrect information a caller has entered, dropped carrier,
time expired, and if the caller failed or passed the Security
Check door.
Security Check will create a file called Caller.dat in the
directory of you choice. This is a database of callers name and
last date checked by Security Check. The way this works, for now
at least, is if a caller is selected by Security Check, then it
will record the callers name and date when he/she was checked..
Therefore, if the caller calls again the same day, then it will
not bother them again that day. If the caller calls back the
next day, or in the future, it will compare the last date called
from the database with your systems date and if they are
different then Security Check may or may not grab them. This
also depends on the chance percent for selection that you enter
in the config file.
02/12/96 - If a new user security level was included between your Min. & Max.
Security level definements in the Config file, Secure Check would
always come up on a new user right after they logged in. I added
support to check the users record now to see if they are a first
time caller, if so, then Secure Check will bypass them that first
logon time.
Updated the Config Maker Util to use the new Graphical inferface
that I now use..
10/25/95 - If a sysop set a callers account time beyond 540 minutes, Secure
Check would show a time expired when the caller tried to log on..
TriBBS currently has a minor bug in the creatation of the Door.sys
when it calulates the Seconds field and would cause a negative
number if a caller time was beyond 540 mins. Mark Goodwin is aware
of this bug and will correct it when he gets the chance. But for
now, I trick, the Secure Check door into using the mins field if
it finds the seconds field with a negative number. This should stop
the "Time Expired" problem. TRICKED! :)
09/04/95 Now allows users to leave up to a 3 line message to the Sysop
Stating why they failed their logon attempt. This message
will be written to the Failed log you specific and to the User
Specific Sreen for the Sysop. This program MUST be registered
inorder for Security Check! to write this information.
08/29/95 Registration Doc's Revisions only!
07/28/95 Reworked some com routines for other type's of BBS software
that uses "Door.sys", but does not follow standard completly.
Basically, If com port is 0, then all other com values are
now set to "NULL".
Corrected more minor typo's in secure.exe program.
Security Check! will now run in local mode if a config file
is NOT specified. All fields will be filled with dummy info.
However, if a sysop enters a config file with a wrong name,
Security Check! will error out and report your problem to
the error.log.
07-19-95 Corrected some minor typo's in both Config.exe and the
main program Secure.exe.
Although Security Check would break the connection and drop
carrier between a Romote caller and the Local end (BBS)
when a caller failed any question, I was allowing Local
mode callers, (Sysops) to continue logging on to the BBS.
Well, this gave the appearence to some Sysops that the
program would not "Drop Carrier".
Well, Folks, you can't Dropped Carrier on someone that is
not calling through a Com Port. Therefore I now force
Security Check to return to the BBS when anyone fails the
any question for either Local or Remote callers.
Caught a problem with the [F1] key in Secure.exe, if someone
hit this key, it would blank the screen.... FIXED!
Forgot to take out the Error trapping routine for the
[ESC] key in Config.exe causing the program stop in the
middle of creating a config file.... FIXED!